-
-
Notifications
You must be signed in to change notification settings - Fork 168
feat(tracing): send both breadcrumbs and logs by default #878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #878 +/- ##
==========================================
+ Coverage 73.33% 73.39% +0.05%
==========================================
Files 64 64
Lines 7423 7423
==========================================
+ Hits 5444 5448 +4
+ Misses 1979 1975 -4 🚀 New features to boost your workflow:
|
One might initialize the |
Introduces a new function
default_event_filter_with_logs
which is the same as the default one but also sends logs for anything at or above INFO.If the
sentry
crate is used with thelogs
feature and there's already a Hub active, grabenable_logs
from the associated client and use the new default filter with logs if possible.If there's no hub, still use the new function that creates logs.
If
enable_logs: false
, the client will drop the logs later anyways.Users still need to opt into sending logs by enabling the feature flag and setting
enable_logs: true
, but this makes it easier if you don't want to set up a custom event filter, and it also makes the onboarding docs simpler.Close #871